-
Notifications
You must be signed in to change notification settings - Fork 241
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
refactor: use common DATA_DIRECTORY env var #10268
base: master
Are you sure you want to change the base?
Conversation
a691cd7
to
89a9b45
Compare
proverBrokerDataDirectory: { | ||
env: 'PROVER_BROKER_DATA_DIRECTORY', | ||
description: 'If starting a prover broker locally, the directory to store broker data', | ||
dataDirectory: { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can ...dataConfigMappings
be done instead?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not without adding a dependency on @aztec/kv-store
to @aztec/circuit-types
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm, it feels wrong then that circuit-types
contains configuration types for apps. It seems much too low level for that.
proverAgentCount: { | ||
env: 'PROVER_AGENT_COUNT', | ||
description: 'The number of prover agents to start', | ||
...numberConfigHelper(1), | ||
}, | ||
dataDirectory: { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
And here
/** Where to store temporary data */ | ||
cacheDir?: string; | ||
|
||
dataDirectory?: string; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you do export type ProverConfig = ActualProverConfig & { blah } & DataStoreConfig;
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same problem, we'd have to depend on kv-store
in circuit-types
This PR removes the custom env var to specify data directories for the prover and broker in favour of using the common config we already have
I have created a separate issue to cleanup the config for the broker/agent/prover/prover-client #10269